Hello, What exactly does Exchange 2003 look for in an email to decide weather the client wants to use RTF of not? I have two seemingly identical clients, one manages to send RTF's out to the Internet, and the other one gets its messages converted to plain text. I can't find any differences between the emails both clients send. The same scenario is true regardless of which user is logged in. Thanks in advance. /Janne

By RTF, I assume that you are talking about Rich Text Format. And thats the option which is in Outlook, if the outlook is set to use RTF/HTML/Pain text, then the users sending mails from that outlook will have that formatting inherited. You can change the same, by going into Outlook, Tools>Options>Mail format, and then check HTML/RTF/Plain Text. If this is not what you were looking for, then elaborate the issue that you are facing.

That is exactly what I'm talking about. I have two Outlook clients, both sening RTF (Rich text format) messages out to the Internet. One of these clients message gets converted by Exchange to plain text, and the other not. That's why I want to know exactly what Exchange looks for in the message when determining that it is an RTF message. As far as I can see (with Outlookspy) bot messages look identical. Why is it then that one client gets their messages converted, and the other doesn't? This behaivour is the same regardless of who is logged on to the client, i.e. it must have something to do with the actual Outlook client, and not user mailbox or user properties. /Janne

As you said its happening on only one client, so lets try to create a new windows profile on that computer. You can also try to delete the OST file from that computer, if that doesnt work then try to create a new user profile. Well if its happening only with one client, irrespective of who has logged in, then the issue is not with the exchange server, its with that particular client. So we need to work in so as to get this client working.

It's actually only one client that manages to send RTF unconverted, all the others gets their converted to plain text. But, as you say, the clients must be constructing RTF's differently. That is why I want to know what the Exchange server looks for when it's evaluating "Determined by individual user settings". Is it possibly if PR_RTF_COMPRESSED is present, or something else?

Exchange server doesn't looks at any settings that are held my the user or client, except whether its configured correctly or not(so that the client can communicate with the server).When a mail is sent from a client (outlook/owa), its just a mail that the exchange server receives, now from here the entire mail flow things begins. So when a mail is sent, it entirely depends upon the client machine, what formatting needs to be applied on that mail, which could be the default settings or the formatting that you applied on that client machine.If it would have been any settings on the exchange server, then the setting would need to have some common factor like an Org Unit (logical container) or mailbox store or any attribute depending upon which the issue is with RTF mails. But thats not the case, as its happening only with the users who log on to that particular machine, so the question of mailbox store or attributes or user settings are ruled out. The only factor that can hamper the situation over ther would be the setting on the client machine.Thus we can say that there is no setting on the exchange server that can cause this issue.The value that you are talking about "PR_RTF_COMPRESSED" is present on the client machine and not on the server. So if a new user profile is created, then all the setting are defualt as a new HKCU is created and you would have all the default settingsAlso check out these links: http://support.microsoft.com/kb/839560http://support.microsoft.com/kb/255621Try with a new user account and let us know what the result were?

I've tracked it down to being entirely based upon wether an inline picture is added somwhere in the body of the message; then it gets through without being converted. If there is no picture in the body, then it gets converted to plain text. The client that managed to send emails out unconverted had an auto-signature containing a small picture, and that's why his mail went through unconverted. The question is still why, though...

I have run into the same thing was beating my head on this. Have you gotten any further on why this is and that simple text formatting gets stripped if no graphics are in-line? I have Exchange 2000 as does one of my clients. I can send formatted text through my client's Exchange but not my own (unless I add graphics). I am using a Smart Host (Comcast) to send e-mail from Exchange, but if I have configure my Outlook to go directly through Comcast's SMTP server, the formatting gets through fine. After myriad testing of various accounts, it definitely seems to be Exchange that is stripping the the formatting..yet I cannot find a configuration option that differs between my Exchange 2000 and my client's Exchange 2000. It's driving me crazy. I suppose I can insert a graphic signature in my messages, but that seems a very inelegent solution. Mike Bruno